Actually, could you give an example of the proxy object that would be passed to the server?

I'm assuming it would be like:

{
  "url": "proxy.host",
  "username": "optional",
  "password": "only_with_username"
}

I'm assuming you wouldn't use a URL likeoptional:only_with_username@proxy.host since the username/password is passed in their own fields but I just want to make sure before I update the README.

Thanks for the help!

Actually, could you give an example of the proxy object that would be passed to the server?

I'm assuming it would be like:

{
  "url": "proxy.host",
  "username": "optional",
  "password": "only_with_username"
}

I'm assuming you wouldn't use a URL likeoptional:only_with_username@proxy.host since the username/password is passed in their own fields but I just want to make sure before I update the README.

Thanks for the help!

Authorization to proxy on chrome is little bit tricky) So yes, there is an object with exactly thats fields in it. I suppose it can be modified so it look cleanier, it was just a hotfix feature i did for myself)

Hey,

can you please update the documentation?

How can I use this feature?

Or should i only do something like

{ "cmd":"request.get", "url":"https://example.com", "userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.0 Safari/537.36", "maxTimeout":60000, "proxy": "??" }

Thanks

I'm pretty sure there is a reason I didn't add it to the docs bc something didn't work right, but you could try passing it like this:

{
  "proxy": {
    "host: "127.0.0.1",
    "port": 1337
  }
}

I'll have to properly look into this issue soon, but I've been busy lately.